This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Wow! ~Phil Reboosiskilen 13.Jan.04 07:06 PM a Web browser Applications Development All ReleasesAll Platforms
Hey Morten,
Once again, thanks for your interest in this weird Notes behavior.
I did what you suggested and added a field called webSaveTime and set it's value to now() in the WebQuerySave agent.
The result is that the document does get saved. If I look at the stored value in the "webSaveTime" field, it is exactly the same as the value stored in the "$Revisions" field.
By the way, these tests were made with a 6.0.3 client and server.
I've been dealing with Notes for many years and I've seen Notes behave in weird ways, but this one is right up there.
My intitial reason for this post was to try and figure out why Notes doesn't recommend calling an explicit save in a "WebQuerysave" agent. I wanted to know this because I want to display a confirmation message to the web user that his or her document was successfully saved without any doubt. A lot of developers simply send a print output telling the user that the document was succesfully saved. This is not really valid, because the document hasn't really been saved yet. If a "WebPOSTSave" event would exist, it would be great and solve my problem. Another strategy is to send a confirmation email using an "On New..." agent, but this is not really what I'm looking for.
Return to top
. . . . . . . . . . . . RE: Wow! (~Phil Reboosisk... 13.Jan.04)
Print this page
